	

	CONGEN TAPE CONTENTS AND INSTRUCTIONS TO BRING UP CONGEN
	--------------------------------------------------------


The following files are on the enclosed 9-track tape, saved using the
BACKUP program -- 1600 BPI, interchange mode:

congen.rel
draw.rel
edits.rel
genera.rel
imbed.rel
prune.rel
stereo.rel
xmn.rel
amnacd.lib
bmterp.lib
bsterp.lib
congen.lib
isopre.lib
surv.lib
tsterp.lib
init.cg0
deppex.mac
rfiles.mac
bcplib.rel
congen.doc
records.cg1
records.cg2
records.cg3
records.cg4
records.cg5


To bring up CONGEN:
-------------------

1. Login to the directory on which you want the CONGEN files to
be. Use the DUMPER program, interchange mode, format 0 to restore the
files from the tape to this directory, e.g.:

    Load the tape onto the drive and press the LOAD/RESET button.

    (In the following example, your input is in lower case.)

    @dumper
    DUMPER>format 0
    DUMPER>interchange
    DUMPER>tape mta0:			(or mta1: or ...)
    DUMPER>restore *.*;* <congen>	(or whatever the directory is)
    ...
    END OF SAVESET
    DUMPER>exit
    @unl mta0:				(or mta1: or ...)

2. Rename record.* to be records.*. For example,
    @ren record.cg1 records.cg1
The recording files were named record.* simply because the BACKUP program
can't handle file names longer than 6 characters.
3. Make a file called deppex.mac containing the following externals:

    MAKDEV	The SIXBIT representation of the device upon which the 
		CONGEN files are stored (e.g., SIXBIT /DSKB/)

    MAKPPN	The PPN of the account under which the CONGEN files are
		stored (e.g., XWD 122,1015)

    SAVEXT	The SIXBIT representation of the extension which the
		runnable CONGEN files will have (e.g., SIXBIT /EXE/)

A sample deppex.mac is included in the files on the tape, but you should
use this as a guide only - the actual values for MAKDEV, MAKPPN and
SAVEXT need to be specified for each different TOPS20 installation.

4. Assemble deppex.mac with MACRO (result: deppex.rel):

    @macro

    *deppex_deppex

    NO ERRORS DETECTED

    PROGRAM BREAK IS 000003
    CPU TIME USED 00:00.208

    15P CORE USED

    *^Z


5. Make a file called rfiles.mac which looks exactly like the
rfiles.mac on the tape, except with the 5 occurrences of "<carhart>"
replaced with the name of the directory with the congen files on it.
rfiles.mac specifies the names of the files that recordings of users'
sessions may be saved on.

6. Assemble rfiles.mac with MACRO (result: rfiles.rel).

7. Separately link (with deppex) and save the following modules:

	draw.rel, edits.rel, genera.rel, prune.rel,
	imbed.rel, stereo.rel, xmn.rel

The link step is demonstrated by the following sequence for linking the
draw module. For the other modules, the appropriate module name should
be substituted where "draw" now appears:

    @link
    *deppex,draw/nosym 
    */s bcplib
    */g

After each module is linked, save the resulting core image as the
runable file whose extension is as specified by SAVEXT in the
deppex.mac file (e.g. draw.exe). The core image has a sharable high
segment and a user-specific low segment.
8. Link congen.rel with deppex and rfiles:

    @link
    *deppex,rfiles,congen/nosym
    */s bcplib
    */g

Save the result with an extension as specified by SAVEXT in the
deppex.mac file (e.g., congen.exe).

9. CONGEN is now ready to be run; to the TOPS20 monitor, type

	congen			(or "run congen" if necessary)

and CONGEN should respond with

	WELCOME TO CONGEN...







NOTES
-----

1. congen.doc is a copy of the CONGEN User's Manual.

2. Users are given the option of having their sessions recorded. Each
time a user exits a session that is being recorded, s/he can specify the
name of a file to create and put the recording in. If no file is
specified, then the recording is appended to records.cg1 (or .cg2 if
.cg1 is concurrently being written to, etc.). Any time a recording file
gets larger than you want to keep around, it may be saved or deleted,
and replaced with a new empty file of the same name. If users don't want
their sessions recorded in a general repository, then they can either
save them in files of their own, or not save them at all.

3. The CONGEN module is the main one (i.e., the one which the user
should RUN). The program uses all eight runnable files, chaining with
the RUN UUO and communicating intermediate results on file.

During the running of CONGEN, temporary files with names nnnTOP.CG,
nnnSTR.CG, nnnSC1.CG, nnnSC2.CG and (if the recording option is chosen)
nnnREC.CG are created, where nnn is the job number.  If CONGEN is
exitted normally, all of these files are cleaned up, but in the event of
a ^C exit, they are left intact.  This is both a benefit and a drawback;
a benefit because at any time the user can abort an unexpectedly lengthy
computation by issuing a ^C, then RUNning CONGEN again (this is a
general escape mechanism in the program, and will always be safe to do),
at which point CONGEN will pick up all pertinent information from the
files; a drawback because the files stay around even if the user does
not RUN CONGEN again - they may clutter up the directory, and may lead
to some confusion if someone later logs in and gets the same job number
(in this case, RUN CONGEN will put the user back in the middle of the
session stored on the .CG files; you can always tell when this has
happened, because you don't get the normal greeting message, but just
the prompt #).
